1.2.1. Vendor 1 testing

Issues found:

  • vendor deletes meeting response from various clients, because there isn’t a correct SEQUENCE number

  • One vendor doesn’t recognize meeting requests caused by TIMEZONE definition — see example:

    EXAMPLE
    BEGIN:VTIMEZONE
    TZID:US/Eastern
    * BEGIN:STANDARD
    * TZOFFSETFROM:-0400
    * TZOFFSETTO:-0500
    * DTSTART:19551030T020000
    * RRULE:FREQ=YEARLY;UNTIL=20061029T060000Z;BYMONTH=10;BYDAY=-1SU
    * TZNAME:EST
    * END:STANDARD
    BEGIN:DAYLIGHT
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:20070311T020000
    RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
    TZNAME:EDT
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:-0400
    TZOFFSETTO:-0500
    DTSTART:20071104T020000
    RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
    TZNAME:EST
    END:STANDARD
    END:VTIMEZONE
  • Meeting request from one vendor is silently deleted from CalDAV scheduling INBOX by another vendor probably caused by a bug in that vendors application

  • iMIP meeting request from one client is not visible in CalDAV INBOX

  • One client Error message “Request error — Calendar not found” appears when user creates new calendar

  • Calendar is successfully created on the server, but the error message appears

  • One client’s provides incorrect free/busy (organizer and attendee are swapped)

  • Free/Busy — Problem with case sensitive MAILTO — FIXED

Test result:

  • 1.1 Ok

  • 1.2 Ok

  • 1.3 Ok

  • 1.4 Ok

  • 2.1 Ok

  • 2.2 Ok

  • 2.3 Ok

  • 2.4 Ok

  • 2.5 Ok

  • 2.6 stored on the server, but some apps aren’t able to display this exception

  • 2.7 Ok

  • 2.8 Ok

  • 2.9 Ok

  • 3.* Not tested

  • 4.1 Ok

  • 4.2 Ok

  • 4.3 Ok

  • 4.4 Ok

  • 4.5 Ok

  • 5.* Not tested

  • 6.1 Ok

  • 6.2 There is a problem when one application creates calendar on a CalDAV. Calendar is created, but other app reports — “Request error — Calendar not found”.

  • 6.3 N/A — app doesn’t support it

  • 6.4 N/A — app doesn’t support it

  • 6.5 Ok

  • 6.6 N/A — app doesn’t support it

  • 7.* Not tested

  • 8.1 Ok

  • 8.2 Mostly Ok, problem with replies from several apps because incorrect SEQUENCE in reply

  • 8.3 Ok

  • 8.4 Ok

  • 8.5 Mostly Ok, the same problem as 8.2

  • 8.6 Ok